Charging over a user-deployed relay

ABSTRACT

Network entities in a wireless network cooperate to account and charge for data communicated over the wireless network. Accounting and charging enable the network entities to properly allocate charges to a second user equipment that communicates through a first user equipment, which acts as a relay in the wireless network. A network entity receives a request from the first user equipment related to a packet data network connection relating to the second user equipment. The network entity establishes or modifies a connection between a gateway and the first user equipment in response to the request. Charges for the data may be allocated to the second user equipment for data communicated with the identifier of the second user equipment.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of U.S. Provisional Application Ser.No. 61/643,094, entitled “Charging Over a User-deployed Relay” and filedon May 4, 2012, which is expressly incorporated by reference herein inits entirety.

BACKGROUND

1. Field

The present disclosure relates generally to communication systems, andmore particularly, to wireless communications devices that operate asuser equipment and relays.

2. Background

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power). Examples of such multiple-access technologies includecode division multiple access (CDMA) systems, time division multipleaccess (TDMA) systems, frequency division multiple access (FDMA)systems, orthogonal frequency division multiple access (OFDMA) systems,single-carrier frequency division multiple access (SC-FDMA) systems, andtime division synchronous code division multiple access (TD-SCDMA)systems.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. An example of an emergingtelecommunication standard is Long Term Evolution (LTE). LTE is a set ofenhancements to the Universal Mobile Telecommunications System (UMTS)mobile standard promulgated by Third Generation Partnership Project(3GPP). It is designed to better support mobile broadband Internetaccess by improving spectral efficiency, lower costs, improve services,make use of new spectrum, and better integrate with other open standardsusing OFDMA on the downlink (DL), SC-FDMA on the uplink (UL), andmultiple-input multiple-output (MIMO) antenna technology. However, asthe demand for mobile broadband access continues to increase, thereexists a need for further improvements in LTE technology. Preferably,these improvements should be applicable to other multi-accesstechnologies and the telecommunication standards that employ thesetechnologies.

SUMMARY

In an aspect of the disclosure, network entities in a wireless networkmay cooperate to account and charge for data communicated over thewireless network. Accounting and charging enable the network entities toproperly allocate charges to a user equipment (UE) that communicatesthrough another UE that acts as a relay in the wireless network.

In an aspect of the disclosure, one or more network entities receive arequest related to a packet data network (PDN) connection from a firstUE. The request may relate to a second UE. The first UE may comprise arelay eNodeB.

In an aspect of the disclosure, the one or more network entities mayestablish or modify a connection between a gateway and the first UE inresponse to the request. Establishing or modifying the connection mayinclude sending an identifier of the second UE to the gateway.

In an aspect of the disclosure, a connection between the gateway and thefirst UE may be established after receiving a request for a PDNconnection which includes an identifier of the first UE and creating aradio bearer for the requested PDN connection. The request for a PDNconnection may also include an identifier of the second UE.

In an aspect of the disclosure, the one or more network entities mayallocate charges to the second UE for data communicated between thefirst UE and the gateway on behalf of the second UE. The charges may beallocated to the second UE based on the identifier of the second UE.Allocating charges for data may include providing a credit to the firstUE for data communicated on behalf of the second UE. Charges may beallocated for the data using a TFT to discriminate between datacorresponding to the first UE and data corresponding to another UE.

In an aspect of the disclosure, a connection between the gateway and thefirst UE may be modified by creating a radio bearer associated with thesecond UE.

In an aspect of the disclosure, a relay eNodeB may establish aconnection with a terminal UE while connected to a PDN through acollocated UE. A connection with a gateway may be established ormodified. Establishing or modifying a connection with the gateway mayinclude sending an identifier of the terminal UE to the gateway.Establishing or modifying a connection with the gateway further includesrequesting a radio bearer associated with the terminal UE.

In an aspect of the disclosure, the relay eNodeB may relay data betweenthe terminal UE and the PDN using the established or modified connectionwith the gateway. The PDN charges are allocated to the terminal UE basedon the data relayed between the terminal UE and the PDN.

In an aspect of the disclosure, the relay eNodeB may receive a creditbased on data relayed between the terminal UE and the PDN.

The PDN charges allocated to the terminal UE may be allocated using atemplate to discriminate between data corresponding to the terminal UEand data corresponding to another UE.

In an aspect of the disclosure, a terminal UE may establish a connectionwith a first eNodeB, which may be a relay. The terminal UE may determinea type of the first eNodeB. The type of the first eNodeB may either bedetermined to be trusted or untrusted. The terminal UE may establish aVPN connection with a gateway when the first eNodeB relays data to asecond eNodeB. PDN data charges may be allocated based on datacommunicated over the VPN connection. A credit for PDN data may beprovided to the eNodeB based on the data communicated through the VPNconnection.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a network architecture.

FIG. 2 is a diagram illustrating an example of an access network.

FIG. 3 is a diagram illustrating an example of a DL frame structure inLTE.

FIG. 4 is a diagram illustrating an example of an UL frame structure inLTE.

FIG. 5 is a diagram illustrating an example of a radio protocolarchitecture for the user and control planes.

FIG. 6 is a diagram illustrating an example of an evolved Node B anduser equipment in an access network.

FIG. 7 is a diagram illustrating a network in which UEs are configuredto provide relay service.

FIG. 8 is a diagram illustrating a UE architected for providing relayservice.

FIG. 9 is a diagram illustrating a UE architected for providing relayservice.

FIG. 10 is a simplified call flow diagram related to a method ofwireless communication.

FIGS. 11A and 11B are diagrams illustrating charging over auser-deployed relay.

FIG. 12 is a diagram illustrating charging over a user-deployed relay.

FIG. 13 is a simplified call flow diagram related to a method ofwireless communication.

FIG. 14 includes flow charts related to a method of wirelesscommunication.

FIG. 15 is a flow chart of a method of wireless communication.

FIG. 16 is a conceptual data flow diagram illustrating the data flowbetween different modules/means/components in an exemplary apparatus.

FIG. 17 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 18 is a conceptual data flow diagram illustrating the data flowbetween different modules/means/components in an exemplary apparatus.

FIG. 19 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 20 is a conceptual data flow diagram illustrating the data flowbetween different modules/means/components in an exemplary apparatus.

FIG. 21 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the only configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purpose of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, modules, components,circuits, steps, processes, algorithms, etc. (collectively referred toas “elements”). These elements may be implemented using electronichardware, computer software, or any combination thereof. Whether suchelements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented with a “processing system”that includes one or more processors. Examples of processors includemicroprocessors, microcontrollers, digital signal processors (DSPs),field programmable gate arrays (FPGAs), programmable logic devices(PLDs), state machines, gated logic, discrete hardware circuits, andother suitable hardware configured to perform the various functionalitydescribed throughout this disclosure. One or more processors in theprocessing system may execute software. Software shall be construedbroadly to mean instructions, instruction sets, code, code segments,program code, programs, subprograms, software modules, applications,software applications, software packages, routines, subroutines,objects, executables, threads of execution, procedures, functions, etc.,whether referred to as software, firmware, middleware, microcode,hardware description language, or otherwise.

Accordingly, in one or more exemplary embodiments, the functionsdescribed may be implemented in hardware, software, firmware, or anycombination thereof. If implemented in software, the functions may bestored on or encoded as one or more instructions or code on acomputer-readable medium. Computer-readable media includes computerstorage media. Storage media may be any available media that can beaccessed by a computer. By way of example, and not limitation, suchcomputer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer. Disk and disc, as used herein, includescompact disc (CD), laser disc, optical disc, digital versatile disc(DVD), floppy disk and Blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

FIG. 1 is a diagram illustrating an LTE network architecture 100. TheLTE network architecture 100 may be referred to as an Evolved PacketSystem (EPS) 100. The EPS 100 may include one or more user equipment(UE) 102, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN)104, an Evolved Packet Core (EPC) 110, a Home Subscriber Server (HSS)120, and an Operator's IP Services 122. The EPS can interconnect withother access networks, but for simplicity those entities/interfaces arenot shown. As shown, the EPS provides packet-switched services, however,as those skilled in the art will readily appreciate, the variousconcepts presented throughout this disclosure may be extended tonetworks providing circuit-switched services.

The E-UTRAN includes the evolved Node B (eNB) 106 and other eNBs 108.The eNB 106 provides user and control planes protocol terminationstoward the UE 102. The eNB 106 may be connected to the other eNBs 108via a backhaul (e.g., an X2 interface). The eNB 106 may also be referredto as a base station, a base transceiver station, a radio base station,a radio transceiver, a transceiver function, a basic service set (BSS),an extended service set (ESS), or some other suitable terminology. TheeNB 106 provides an access point to the EPC 110 for a UE 102. Examplesof UEs 102 include a cellular phone, a smart phone, a session initiationprotocol (SIP) phone, a laptop, a personal digital assistant (PDA), asatellite radio, a global positioning system, a multimedia device, avideo device, a digital audio player (e.g., MP3 player), a camera, agame console, or any other similar functioning device. The UE 102 mayalso be referred to by those skilled in the art as a mobile station, asubscriber station, a mobile unit, a subscriber unit, a wireless unit, aremote unit, a mobile device, a wireless device, a wirelesscommunications device, a remote device, a mobile subscriber station, anaccess terminal, a mobile terminal, a wireless terminal, a remoteterminal, a handset, a user agent, a mobile client, a client, or someother suitable terminology.

The eNB 106 is connected by an Si interface to the EPC 110. The EPC 110includes a Mobility Management Entity (MME) 112, other MMEs 114, aServing Gateway 116, and a Packet Data Network (PDN) Gateway 118. TheMME 112 is the control node that processes the signaling between the UE102 and the EPC 110. Generally, the MME 112 provides bearer andconnection management. All user IP packets are transferred through theServing Gateway 116, which itself is connected to the PDN Gateway 118.The PDN Gateway 118 provides UE IP address allocation as well as otherfunctions. The PDN Gateway 118 is connected to the Operator's IPServices 122. The Operator's IP Services 122 may include the Internet,the Intranet, an IP Multimedia Subsystem (IMS), and a PS StreamingService (PSS).

FIG. 2 is a diagram illustrating an example of an access network 200 inan LTE network architecture. In this example, the access network 200 isdivided into a number of cellular regions (cells) 202. One or more lowerpower class eNBs 208 may have cellular regions 210 that overlap with oneor more of the cells 202. The lower power class eNB 208 may be a femtocell (e.g., home eNB (HeNB)), pico cell, micro cell, or remote radiohead (RRH). The macro eNBs 204 are each assigned to a respective cell202 and are configured to provide an access point to the EPC 110 for allthe UEs 206 in the cells 202. There is no centralized controller in thisexample of an access network 200, but a centralized controller may beused in alternative configurations. The eNBs 204 are responsible for allradio related functions including radio bearer control, admissioncontrol, mobility control, scheduling, security, and connectivity to theserving gateway 116.

The modulation and multiple access scheme employed by the access network200 may vary depending on the particular telecommunications standardbeing deployed. In LTE applications, OFDM is used on the DL and SC-FDMAis used on the UL to support both frequency division duplexing (FDD) andtime division duplexing (TDD). As those skilled in the art will readilyappreciate from the detailed description to follow, the various conceptspresented herein are well suited for LTE applications. However, theseconcepts may be readily extended to other telecommunication standardsemploying other modulation and multiple access techniques. By way ofexample, these concepts may be extended to Evolution-Data Optimized(EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interfacestandards promulgated by the 3rd Generation Partnership Project 2(3GPP2) as part of the CDMA2000 family of standards and employs CDMA toprovide broadband Internet access to mobile stations. These concepts mayalso be extended to Universal Terrestrial Radio Access (UTRA) employingWideband-CDMA (W-CDMA) and other variants of CDMA, such as TD-SCDMA;Global System for Mobile Communications (GSM) employing TDMA; andEvolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, and Flash-OFDM employing OFDMA. UTRA, E-UTRA, UMTS, LTE and GSMare described in documents from the 3GPP organization. CDMA2000 and UMBare described in documents from the 3GPP2 organization. The actualwireless communication standard and the multiple access technologyemployed will depend on the specific application and the overall designconstraints imposed on the system.

The eNBs 204 may have multiple antennas supporting MIMO technology. Theuse of MIMO technology enables the eNBs 204 to exploit the spatialdomain to support spatial multiplexing, beamforming, and transmitdiversity. Spatial multiplexing may be used to transmit differentstreams of data simultaneously on the same frequency. The data steamsmay be transmitted to a single UE 206 to increase the data rate or tomultiple UEs 206 to increase the overall system capacity. This isachieved by spatially precoding each data stream (i.e., applying ascaling of an amplitude and a phase) and then transmitting eachspatially precoded stream through multiple transmit antennas on the DL.The spatially precoded data streams arrive at the UE(s) 206 withdifferent spatial signatures, which enables each of the UE(s) 206 torecover the one or more data streams destined for that UE 206. On theUL, each UE 206 transmits a spatially precoded data stream, whichenables the eNB 204 to identify the source of each spatially precodeddata stream.

Spatial multiplexing is generally used when channel conditions are good.When channel conditions are less favorable, beamforming may be used tofocus the transmission energy in one or more directions. This may beachieved by spatially precoding the data for transmission throughmultiple antennas. To achieve good coverage at the edges of the cell, asingle stream beamforming transmission may be used in combination withtransmit diversity.

In the detailed description that follows, various aspects of an accessnetwork will be described with reference to a MIMO system supportingOFDM on the DL. OFDM is a spread-spectrum technique that modulates dataover a number of subcarriers within an OFDM symbol. The subcarriers arespaced apart at precise frequencies. The spacing provides“orthogonality” that enables a receiver to recover the data from thesubcarriers. In the time domain, a guard interval (e.g., cyclic prefix)may be added to each OFDM symbol to combat inter-OFDM-symbolinterference. The UL may use SC-FDMA in the form of a DFT-spread OFDMsignal to compensate for high peak-to-average power ratio (PAPR).

FIG. 3 is a diagram 300 illustrating an example of a DL frame structurein LTE. A frame (10 ms) may be divided into 10 equally sized sub-frames.Each sub-frame may include two consecutive time slots. A resource gridmay be used to represent two time slots, each time slot including aresource block. The resource grid is divided into multiple resourceelements. In LTE, a resource block contains 12 consecutive subcarriersin the frequency domain and, for a normal cyclic prefix in each OFDMsymbol, 7 consecutive OFDM symbols in the time domain, or 84 resourceelements. For an extended cyclic prefix, a resource block contains 6consecutive OFDM symbols in the time domain and has 72 resourceelements. Some of the resource elements, as indicated as R 302, 304,include DL reference signals (DL-RS). The DL-RS include Cell-specific RS(CRS) (also sometimes called common RS) 302 and UE-specific RS (UE-RS)304. UE-RS 304 are transmitted only on the resource blocks upon whichthe corresponding physical DL shared channel (PDSCH) is mapped. Thenumber of bits carried by each resource element depends on themodulation scheme. Thus, the more resource blocks that a UE receives andthe higher the modulation scheme, the higher the data rate for the UE.

FIG. 4 is a diagram 400 illustrating an example of an UL frame structurein LTE. The available resource blocks for the UL may be partitioned intoa data section and a control section. The control section may be formedat the two edges of the system bandwidth and may have a configurablesize. The resource blocks in the control section may be assigned to UEsfor transmission of control information. The data section may includeall resource blocks not included in the control section. The UL framestructure results in the data section including contiguous subcarriers,which may allow a single UE to be assigned all of the contiguoussubcarriers in the data section.

A UE may be assigned resource blocks 410 a, 410 b in the control sectionto transmit control information to an eNB. The UE may also be assignedresource blocks 420 a, 420 b in the data section to transmit data to theeNB. The UE may transmit control information in a physical UL controlchannel (PUCCH) on the assigned resource blocks in the control section.The UE may transmit only data or both data and control information in aphysical UL shared channel (PUSCH) on the assigned resource blocks inthe data section. A UL transmission may span both slots of a subframeand may hop across frequency.

A set of resource blocks may be used to perform initial system accessand achieve UL synchronization in a physical random access channel(PRACH) 430. The PRACH 430 carries a random sequence and cannot carryany UL data/signaling. Each random access preamble occupies a bandwidthcorresponding to six consecutive resource blocks. The starting frequencyis specified by the network. That is, the transmission of the randomaccess preamble is restricted to certain time and frequency resources.There is no frequency hopping for the PRACH. The PRACH attempt iscarried in a single subframe (1 ms) or in a sequence of few contiguoussubframes and a UE can make only a single PRACH attempt per frame (10ms).

FIG. 5 is a diagram 500 illustrating an example of a radio protocolarchitecture for the user and control planes in LTE. The radio protocolarchitecture for the UE and the eNB is shown with three layers: Layer 1,Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer andimplements various physical layer signal processing functions. The L1layer will be referred to herein as the physical layer 506. Layer 2 (L2layer) 508 is above the physical layer 506 and is responsible for thelink between the UE and eNB over the physical layer 506.

In the user plane, the L2 layer 508 includes a media access control(MAC) sublayer 510, a radio link control (RLC) sublayer 512, and apacket data convergence protocol (PDCP) 514 sublayer, which areterminated at the eNB on the network side. Although not shown, the UEmay have several upper layers above the L2 layer 508 including a networklayer (e.g., IP layer) that is terminated at the PDN gateway 118 on thenetwork side, and an application layer that is terminated at the otherend of the connection (e.g., far end UE, server, etc.).

The PDCP sublayer 514 provides multiplexing between different radiobearers and logical channels. The PDCP sublayer 514 also provides headercompression for upper layer data packets to reduce radio transmissionoverhead, security by ciphering the data packets, and handover supportfor UEs between eNBs. The RLC sublayer 512 provides segmentation andreassembly of upper layer data packets, retransmission of lost datapackets, and reordering of data packets to compensate for out-of-orderreception due to hybrid automatic repeat request (HARQ). The MACsublayer 510 provides multiplexing between logical and transportchannels. The MAC sublayer 510 is also responsible for allocating thevarious radio resources (e.g., resource blocks) in one cell among theUEs. The MAC sublayer 510 is also responsible for HARQ operations.

In the control plane, the radio protocol architecture for the UE and eNBis substantially the same for the physical layer 506 and the L2 layer508 with the exception that there is no header compression function forthe control plane. The control plane also includes a radio resourcecontrol (RRC) sublayer 516 in Layer 3 (L3 layer). The RRC sublayer 516is responsible for obtaining radio resources (i.e., radio bearers) andfor configuring the lower layers using RRC signaling between the eNB andthe UE.

FIG. 6 is a block diagram of an eNB 610 in communication with a UE 650in an access network. In the DL, upper layer packets from the corenetwork are provided to a controller/processor 675. Thecontroller/processor 675 implements the functionality of the L2 layer.In the DL, the controller/processor 675 provides header compression,ciphering, packet segmentation and reordering, multiplexing betweenlogical and transport channels, and radio resource allocations to the UE650 based on various priority metrics. The controller/processor 675 isalso responsible for HARQ operations, retransmission of lost packets,and signaling to the UE 650.

The transmit (TX) processor 616 implements various signal processingfunctions for the L1 layer (i.e., physical layer). The signal processingfunctions includes coding and interleaving to facilitate forward errorcorrection (FEC) at the UE 650 and mapping to signal constellationsbased on various modulation schemes (e.g., binary phase-shift keying(BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying(M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded andmodulated symbols are then split into parallel streams. Each stream isthen mapped to an OFDM subcarrier, multiplexed with a reference signal(e.g., pilot) in the time and/or frequency domain, and then combinedtogether using an Inverse Fast Fourier Transform (IFFT) to produce aphysical channel carrying a time domain OFDM symbol stream. The OFDMstream is spatially precoded to produce multiple spatial streams.Channel estimates from a channel estimator 674 may be used to determinethe coding and modulation scheme, as well as for spatial processing. Thechannel estimate may be derived from a reference signal and/or channelcondition feedback transmitted by the UE 650. Each spatial stream isthen provided to a different antenna 620 via a separate transmitter618TX. Each transmitter 618TX modulates an RF carrier with a respectivespatial stream for transmission.

At the UE 650, each receiver 654RX receives a signal through itsrespective antenna 652. Each receiver 654RX recovers informationmodulated onto an RF carrier and provides the information to the receive(RX) processor 656. The RX processor 656 implements various signalprocessing functions of the L1 layer. The RX processor 656 performsspatial processing on the information to recover any spatial streamsdestined for the UE 650. If multiple spatial streams are destined forthe UE 650, they may be combined by the RX processor 656 into a singleOFDM symbol stream. The RX processor 656 then converts the OFDM symbolstream from the time-domain to the frequency domain using a Fast FourierTransform (FFT). The frequency domain signal comprises a separate OFDMsymbol stream for each subcarrier of the OFDM signal. The symbols oneach subcarrier, and the reference signal, is recovered and demodulatedby determining the most likely signal constellation points transmittedby the eNB 610. These soft decisions may be based on channel estimatescomputed by the channel estimator 658. The soft decisions are thendecoded and deinterleaved to recover the data and control signals thatwere originally transmitted by the eNB 610 on the physical channel. Thedata and control signals are then provided to the controller/processor659.

The controller/processor 659 implements the L2 layer. Thecontroller/processor can be associated with a memory 660 that storesprogram codes and data. The memory 660 may be referred to as acomputer-readable medium. In the UL, the controller/processor 659provides demultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover upper layer packets from the core network. The upper layerpackets are then provided to a data sink 662, which represents all theprotocol layers above the L2 layer. Various control signals may also beprovided to the data sink 662 for L3 processing. Thecontroller/processor 659 is also responsible for error detection usingan acknowledgement (ACK) and/or negative acknowledgement (NACK) protocolto support HARQ operations.

In the UL, a data source 667 is used to provide upper layer packets tothe controller/processor 659. The data source 667 represents allprotocol layers above the L2 layer. Similar to the functionalitydescribed in connection with the DL transmission by the eNB 610, thecontroller/processor 659 implements the L2 layer for the user plane andthe control plane by providing header compression, ciphering, packetsegmentation and reordering, and multiplexing between logical andtransport channels based on radio resource allocations by the eNB 610.The controller/processor 659 is also responsible for HARQ operations,retransmission of lost packets, and signaling to the eNB 610.

Channel estimates derived by a channel estimator 658 from a referencesignal or feedback transmitted by the eNB 610 may be used by the TXprocessor 668 to select the appropriate coding and modulation schemes,and to facilitate spatial processing. The spatial streams generated bythe TX processor 668 are provided to different antenna 652 via separatetransmitters 654TX. Each transmitter 654TX modulates an RF carrier witha respective spatial stream for transmission.

The UL transmission is processed at the eNB 610 in a manner similar tothat described in connection with the receiver function at the UE 650.Each receiver 618RX receives a signal through its respective antenna620. Each receiver 618RX recovers information modulated onto an RFcarrier and provides the information to a RX processor 670. The RXprocessor 670 may implement the L1 layer.

The controller/processor 675 implements the L2 layer. Thecontroller/processor 675 can be associated with a memory 676 that storesprogram codes and data. The memory 676 may be referred to as acomputer-readable medium. In the UL, the control/processor 675 providesdemultiplexing between transport and logical channels, packetreassembly, deciphering, header decompression, control signal processingto recover upper layer packets from the UE 650. Upper layer packets fromthe controller/processor 675 may be provided to the core network. Thecontroller/processor 675 is also responsible for error detection usingan ACK and/or NACK protocol to support HARQ operations.

FIG. 7 is a diagram 700 illustrating a network in which a UE eNodeB(UeNB) 702 or 704 provides network connectivity to a terminal UE (TUE)712 or 714. UeNB 702 or 704 may advertise its availability to serve asan eNodeB, which provides network connectivity for other TUEs 712 or714. In one example, UeNB 704 has a wireless backhaul 708, which mayinclude LTE in a licensed spectrum, and UeNB 704 may provide networkservices to TUE 714 through a wireless access channel 718. In anotherexample, UeNB 702 has a wired backhaul 706 and provides network servicesto TUE 712 through a wireless access channel 716.

On the access-hop 716 and 718, both UeNBs 702 and 704 behave essentiallylike a cell, from the PHY-MAC perspective. The UeNBs 702 and 704 mayincorporate certain power-saving techniques in addition to thoseemployed by a typical eNB 710 or network-relay (not shown).

In the example of FIG. 7, UeNB 702 provides a backhaul as a wireddevice, while

UeNB 704 provides a wireless backhaul. When functioning as a relay, UeNB704 may operate as both an eNB and a UE. UeNB 704 communicates withdonor eNB 710 on the backhaul 708, behaving essentially like a UE, froma physical/MAC layer (PHY-MAC) perspective. During periods of lowtraffic activity, the UeNB 704 may go into discontinuous reception (DRX)mode, or idle mode, on the backhaul hop 708 for power-saving ornetwork-load-alleviation purposes.

UeNB 704 may provide backhaul over LTE or another Radio AccessTechnology (RAT), such as GSM, 1x/DO, etc. UeNB 704 is typically inconnected mode on the backhaul link if it is actively connected to anyTUEs 714, which are actively transmitting data. UeNB 704 may be in DRXmode on the backhaul link if all the connected TUEs 714 are also in DRXmode. When UeNB 704 is released by the network on the backhaul link, allthe connected TUEs 714 are typically released by the UeNB 704.

The UeNB 704 may be in RRC idle or RRC connected mode on the backhaul toadvertise access to TUEs 712, 714 when no TUEs 712 or 714 are connectedto UeNB 704. In some embodiments, UeNB 704 refrains from using RRC idlemode on the backhaul link in favor of using DRX mode in order toconserve battery power without causing longer overall call setup timefor TUE 714.

If UeNB 704 is in RRC idle mode on the backhaul link when a TUE 714attempts to establish a connection, then the UeNB 704 typicallyestablishes a connection on the backhaul link in order to authorize theTUE 714 for service. UeNB 704 typically refrains from advertisingservice if it is not camped on a suitable cell on the backhaul link.

In the architectures and diagrams discussed in FIGS. 8, 9, 11A, 11B, and12, the labels “Uu,” “Un,” “S1-U,” “S1-MME,” “S11,” “S5/S8,” “S6a,”“TR-069,” and “SGi” indicate interfaces and/or communication protocolsthat are known in the art and, therefore, will not be discussed indetail herein.

FIG. 8 is a diagram 800 illustrating an example of UeNB architecturethat may be used with user-deployed UeNB 702. When TUE 712 is camped ona RAN through a connection to a home eNodeB (HeNB) 802, a local IPaccess (LIPA) PDN gateway 804 provides a data plane and may provide aconnection to the PDN 825 to bypass core network (CN) 820 for dataservices. For example, the PDN 825 may be the Internet. Any suitablenetwork architecture defined for LIPA may be reused for connectivity ofTUE 712, but limited mobility services may be available for TUE 712 thatis connecting to or from LIPA PDN. The TUE 712 typically attempts toestablish the LIPA PDN connection upon each handover to HeNB 802. A PDNconnection through the core network 820 may be unavailable for data usebased on operator policies or preferences.

A home eNodeB management system (HeMS) 806 may use network operation andmaintenance (OAM) data and services and be remotely configured andmanaged using standardized protocols such as TR-069 that may be adaptedfor use with HeNB 802. The control plane may remain centralized usingthe MME 808, serving gateway (SGW) 810, and a home subscriber server(HSS) 812, which maintains subscription-related information thatsupports the call handling.

FIG. 9 is a diagram 900 illustrating an example of an architecture usedwith UeNB 704. In this example, TUE 714 is served by one or moregateways 924, 922 in the core network 920, such as PDN gateway 922. UeNB704 need not have a local PDN gateway. An e-UTRAN 910 comprising UeNB704 and eNB 906. UeNB 704 comprises an eNB 902 and a UE 904. UeNB 704may act as a relay for eNB 906.

Certain embodiments provide systems and methods for accounting andcharging related to network usage involving UeNBs 702 and 704. Anoperator of a network may wish to assign usage charges to the TUE 712 or714 that is responsible for the network traffic through UeNB 702 or 704.UeNB 702 and 704 can relay data on behalf of TUE 712 or 714 and can alsogenerate network traffic. Accordingly, assignment of usage chargestypically requires identification of the UE responsible for the traffic.A network operator may assign charges for data usage by UeNB 702 or 704to TUE 712 or 714 and provide an equivalent credit to UeNB 702 or 704.The network operator may select a mode identifying the UE responsiblefor network traffic based on the trustworthiness of UeNB 702 or 704.UeNB 704 may be untrustworthy if, for example, it is configured tobundle its own transmissions with transmissions from one or more TUE 712or 714, such that usage cannot be properly assigned, resulting incharges and credits being inappropriately applied.

Charging for TUE 714 access of a UeNB 704 may be implemented by anetwork entity of the operator network when the UeNB 704 is connected byan LTE or UMTS backhaul. In some embodiments, an element of the UeNB 704may account for network usage charges on the UeNB 704 access network.For example, a local gateway 804 (see FIG. 8) collocated with UeNB 702or 704 may handle accounting functions such as using hot-lining, whichmay involve monitoring traffic by redirecting traffic to a redirectserver.

Charging for network usage related to UeNB 702 or 704 may be controlledand managed by an entity of the operator network 920 and/or by the UeNB702 or 704. In one example, UeNB 702 or 704 may be configured toimplement certain predefined procedures that determine when to triggercharging in the network after a TUE 712 or 714 establishes a connection.

For UeNB 702 or 704 initiated procedures, charging and accountingfunctionality is typically provided by serving gateway/PDN gateway(PGW/SGW) 922 of operator network 920. The PGW/SGW 922 may collect andreport accounting information for each connected TUE 712, 714.Accounting information may identify the amount of data transmitted inuplink and downlink directions, and may be categorized using a qualityof service (QoS) class identifier (QCI) and allocation and retentionpriority (ARP) pair per UE per PDN connection. QCI may include aparameter of the QoS profile of an EPS bearer and is typically a scalarwhich refers to access node-specific parameters that controlbearer-level packet forwarding treatment such as scheduling weights,admission thresholds, queue management thresholds, link layer protocolconfiguration. ARP may be a parameter of the QoS profile of the EPSbearer related to bearer establishment/modification decisions. Theaccounting information may be collected and reported on a per-bearerbasis.

The PGW may provide charging functionality for each TUE 712, 714according to standards-defined procedures. In some embodiments,procedures define methods for charging associated with a PDN connectionusing an international mobile subscriber identity (IMSI) of a TUE 712 or714 that is connected to the UeNB 702 or 704. In some embodiments,charging is performed at the operator network upon creation of a new PDNconnection. One method for charging at the operator network includesestablishing a new PDN connection for each TUE 712 or 714 connected tothe UeNB 702 or 704 using UE-requested PDN connectivity procedures.

With reference again to FIG. 8, an operator network may identify the TUE712 associated with the PDN connection using an IMSI included by theUeNB 702 in the PDN connection request message, when a gateway 804 iscollocated with the UeNB 702. In one example, an information element(IE) may be defined to identify the IMSI. In another example, the IMSImay be included as part of a request for access point name (APN).Traffic associated with the PDN connection can then be charged to theIMSI.

With reference again to FIG. 9, UeNB 704 may use a separate PDNconnection to the core network 920 to indicate that this traffic isexclusively relay traffic for TUE 714, when a PGW/SGW 922 located incore network 920 is used. In this case. PGW/SGW 924 for the relay (shownas PGW/SGW (relay) 924 in FIG. 9) may be configured to permit only GPRStunneling protocol (GTP) traffic directed to an appropriate servinggateway target to pass through the packet data network. All othertraffic may be dropped to ensure that the UeNB 714 does not inserttraffic on the packet data network connection to get free service for UE904 for another UE at the expense of the charged TUE 714.

In certain embodiments, the operator network implements accounting andcharging using a procedure based on modify bearer requests. Modifybearer requests are typically used when a local gateway 804 iscollocated with an HeNB 802 in UeNB 702 (see FIG. 8). Usage charges maybe identified and allocated to TUE 712 when a new PDN connection isrequested for each connected TUE 712. Each PDN connection requires aradio bearer to be allocated to the UeNB 702, and the number of radiobearers available to the UeNB 702 on the backhaul may be subject to apredefined limit. For example, a UeNB 702 may be limited toapproximately 8 radio bearers.

When the UeNB 702 has limited availability of radio bearers, TUE 712 maybe identified for the purposes of accounting and charging through atraffic flow template (TFT). TFTs may discriminate between differentuser payloads using Internet Protocol (IP) header information such assource and destination IP addresses and transmission control protocol(TCP) port numbers. In normal use, TFTs may be used to filter packetsfor voice over IP (VoIP) from lower priority traffic such as webbrowsing traffic in order to assign an appropriate QoS. In someembodiments, UeNB 702 may use network address translation (NAT) forconnecting TUE 712 to an IPv4 network. The UeNB 702 can assign aspecific range of ports to each connected TUE 712.

FIG. 10 illustrates an example call flow 1000 in which UeNB 702 uses themodify bearer request procedure to enable charging for a connected TUE712 at the operator network 920. In FIG. 10, TUE 712 establishes, at1010, a connection at the UeNB 702. UeNB 702 may send, at 1012, a newlydefined Si message comprising a new TUE 712 information report to theMME 808 identifying TUE 712 as having established a connection. TUE 712may be identified by its IMSI and any service flows associated with TUE712 may be identified by the IMSI. The service flows associated with theTUE 712 may be unique to the TUE 712 under the UeNB 702. In someembodiments, new IEs may be added to an existing NAS message to describethe IMSI and associated service flows via TFTs to the MME 808.

Charging for UeNB 702 access at the operator network 920 may be enabledby a request by PDN gateway 1004 for user information corresponding toUeNB 702. In response to such request, then at 1014 the MME 808 may senda modify bearer request message to the serving gateway 1002 thatincludes UeNB 702 user information IE. UeNB 702 user informationincludes the IMSI of the TUE 712 as well as the TFT of any service flowsassociated with the TUE 712. The serving gateway 1002 may send a modifybearer request at 1016 to one or more PDN gateways 1004, including UeNB702 information IE received from MME 808. A modify bearer responsemessage 1018 may be returned to the serving gateway 1002 by the PDNgateway 1004.

At 1020, the serving gateway 1002 sends the modify bearer responsemessage to MME 808. At 1022, the MME 808 sends a new TUE 712 informationACK S1 message to the UeNB 702. A similar procedure may be performedwhen the TUE 712 is either released or performs a handover away from theUeNB 702 to stop the charging.

FIG. 11A is a diagram 1100 illustrating a method of charging at theoperator network using a home agent (HA)/packet gateway (P-GW) 1108,which is typically used when a packet gateway 1102 is collocated withUeNB 702. Diagram 11A includes MME 1102, SGW 1104, and HSS 1106 are UeNBEPC network elements, where MME 1102, SGW 1104, and HSS 1106 are incommunication with UeNB 702. In some embodiments, the TUE 712establishes a VPN tunnel 1120 during PDN gateway 922 connectionestablishment. In the configuration of FIG. 11A, the VPN tunnel 1120 maybe established using an S2C interface. TUE 712 may employ a procedurethat is similar to procedures used for PDN connection Wi-Fi and 3GPPaccess networks.

In one example, TUE 712 may use an IP security (IPsec) tunnel for dataconnections while communicating through UeNB 702. In this example, UeNB702 may use a special access point name (APN) for all TUE 712 traffic.In some embodiments, TUE 712 may be required to establish an IPSectunnel with HA/P-GW 1108 in order to receive data service and PDNgateway 922 may block all traffic that is not sent to the HA/P-GW 1108.

Use of HA/P-GW 1108 for charging may employ existing procedures in theoperator network for managing interactions with MME 808 and PGW/SGW 922,and charging and accounting may be enforced by causing traffic to berouted through the HA/P-GW 1108. In some embodiments, additionalmeasures may be implemented to provide limited access to local service.

FIG. 11B is a diagram 1101 illustrating a method of charging at theoperator network using an evolved packet data gateway (ePDG) 1109 whenusing an untrusted access to the operator network. The TUE 712establishes a VPN tunnel 1121 during PDN gateway 922 connectionestablishment. In the configuration of FIG. 11B, the VPN tunnel 1121 maybe established using an S2B interface.

In one example, TUE 712 may use an IPsec tunnel for data connectionswhile communicating through UeNB 702. In this example, UeNB 702 may usea special APN for all TUE 712 traffic. Untrusted access is routed to theePDG 1109, which provides security mechanisms for connections with TUEsover an untrusted access.

FIG. 12 illustrates an architecture 1200 that may be used with an LTEbackhaul.

Architecture 1200 includes UeNB 702, LTE backhaul 1210, and a UeNB andDeNB Core network control plane 1220. The LTE backhaul 1210 includes eNB906, SGW (UE relay) 1202, and PGW (UE Relay) 1204. The UeNB and DeNBCore network control plane 1220 includes HeMS 806, SGW 924, MME 808, andHSS 812. UeNB 702 may be deployed for any type of access connection andany type of backhaul connection and is usable with any of a plurality ofnetworks, including legacy cellular networks, wired networks, Wi-Finetworks, etc.

Certain embodiments implement procedures for IP address allocation forthe TUE 712. These procedures may include standards-defined proceduresand/or procedures adapted according to certain aspects of the invention.In one example, TUE 712 may be assigned an IP address by the UeNB 702during the default bearer activation. In an IPv4 network, the TUE 712may use IPv4 address allocation via default bearer activation. In anIPv6 network, the TUE 712 may uses /64 IPv6 prefix allocation via IPv6Stateless Address autoconfiguration.

In another example, TUE 712 may indicate to the network within theProtocol Configuration Options element that the TUE 712 wants to obtainthe IP address through DHCP. In an IPv4 network, the TUE 712 uses IPv4address allocation and IPv4 parameter configuration after the attachprocedure via DHCPv4. In an IPv6 network, the TUE 712 uses IPv6parameter configuration via Stateless DHCPv6. The TUE 712 mayadditionally request the allocation of IPv6 prefixes using DHCPv6.

Certain embodiments implement procedures for IP address allocation forthe UeNB 702. These procedures may include standards, definedprocedures, and/or procures adapted according to certain aspects of theinvention. For example, the procedures may include methods currentlyused for IP address allocation for WLAN IP address allocation or for aPGW in the WWAN.

In some embodiments, UeNB 702 may assign an IP address to the TUE 712 inan IPv4 network and/or an IPv6 network. In an IPv4 network the UeNB 702allocates an unused private IPv4 address for use by the TUE 712 and maystart a NAT engine for the purpose of Network Address and PortTranslation. UeNB 702 may then assign the allocated IP address to theTUE 712 via NAS signaling for default bearer activation or DHCP.

FIG. 13 illustrates a call flow 1300 for allocating an IPv6 address tothe TUE 712 by UeNB 702 after an attach procedure 1302. In someembodiments, the UeNB 702 determines that DHCPv6 should be used toobtain an IPv6 address. At 1304, the UeNB 702 may use prefix delegationoptions in DHCPv6 to obtain a /48 IPv6 address prefix for EPS Backhaul.At 1306, UeNB 702 may allocate a unique /64 IPv6 prefix from within the/48 IPv6 prefix for use by the TUE 712. UeNB 702 may then assign, at1310, the allocated IP address to the TUE 712 via NAS signaling fordefault bearer activation or DHCPv6, completing the attach procedure at1308.

FIG. 14 includes a flow chart 1400 of a method of wirelesscommunication. The method may be performed, at least in part, by one ormore network entities that may include an MME 808.

At step 1402, the one or more network entities receive a request relatedto a PDN connection from a first UE 702. The first UE 702 may be a relayeNodeB. The request may relate to a second TUE 712 or 714.

At step 1404, the one or more network entities establish or modify aconnection between a gateway 810 and the first UE 702 in response to therequest. Establishing or modifying the connection may include sending anidentifier of the second UE to the gateway. The gateway 922 or 924 maybe provided in a core network entity 920. The gateway may include one ormore of a PDN gateway 922, a serving gateway 924, a serving generalpacket radio service (GPRS) support node and a gateway GPRS supportnode. A connection between the gateway 922 or 924 and the second UE 712or 714 may be established after receiving a request for a PDN connectionwhich includes an identifier of the second UE 712 or 714. A connectionbetween the gateway 922 or 924 and the second UE 712 or 714 may includecreating a radio bearer for the requested PDN connection. Charges forthe data may be allocated to the second UE 712 or 714 for datacommunicated over the created radio bearer. Charges for the data may beallocated to the second UE 712 or 714 for data communicated with theidentifier of the second UE 712 or 714. The identifier of the second UE712 or 714 may comprise an IMSI of the second UE 712 or 714.

At step 1406, the one or more network entities allocate charges for datato the first UE 702 and the second UE 712 or 714 based on datacommunicated between the first UE 702 and the gateway 922 or 924 onbehalf of the second UE 712 or 714. The one or more network entities mayallocate charges for data by allocating charges to the second UE 712 or714 for data communicated between the second UE 712 or 714 and the PDN825 through the relay eNodeB 702 and the gateway 922 or 924. The one ormore network entities may allocate charges for data includes providing acredit to the first UE 702 for data communicated between the second UE712 or 714 and the network through the relay eNodeB 702 and the gateway922 or 924. Charges may be allocated for the data using a TFT todiscriminate between data corresponding to the second UE 712 or 714 anddata corresponding to another UE. The TFT may identify one or more TCPports allocated to the second UE 712 or 714 by the relay eNodeB 702.

In some embodiments, modifying a connection between the gateway 922 or924 and the second UE 712 or 714 includes creating a radio bearerassociated with the second UE 712 or 714. Charges for the data may beallocated to the second UE 712 or 714 for data communicated using theradio bearer associated with the second UE 712 or 714. Charges for thedata may be allocated based on the data communicated by the first UE 702behalf of the second UE 712 or 714 at a PDN gateway 924. Charges may beallocated for the data by accounting for data communicated through a VPNconnection on behalf of the second UE 712 or 714. A VPN home agent mayidentify the data communicated through the VPN connection on behalf ofthe second UE 712 or 714. Charges for network usage may be allocated byproviding a credit to the first UE 702 for data communicated through theVPN connection on behalf of the second UE 712 or 714.

FIG. 14 further includes a flow chart 1450 of a method of wirelesscommunication. The method may be performed by a UeNB 702.

At step 1452, the UeNB 702 establishes a connection with a TUE 712 or714 while connected to a PDN 825 through a collocated UE.

At step 1454, the UeNB 702 establishes or modifies a connection with agateway. The gateway may include one or more of a PDN gateway 922, aserving gateway 924, a serving GPRS support node and a gateway GPRSsupport node. Establishing or modifying a connection with the gateway922 may include requesting a radio bearer associated with the TUE 712 or714.

At step 1456, the UeNB 702 relays data between the TUE 712 or 714 andthe PDN using the established or modified connection with the gateway.The PDN charges are allocated to the TUE 712 or 714 based on the datarelayed between the TUE 712 or 714 and the PDN. The PDN charges may beallocated to the TUE 712 or 714 are allocated based on data communicatedover the requested radio bearer. The PDN charges allocated to the TUE712 or 714 may be allocated using a TFT to discriminate between datacorresponding to the TUE 712 or 714 and data corresponding to anotherUE. One or more TCP ports may be identified in the TFT, and the PDNcharges allocated to the TUE 712 or 714 may be allocated based on a TCPport used to relay the data between the TUE 712 or 714 and the PDN.

At step 1458, the UeNB 702 a credit is received that is based on thedata relayed between the TUE 712 or 714 and the PDN.

FIG. 15 includes a flow chart 1500 of a method of wirelesscommunication. The method may be performed by a TUE 714. At step 1502,the TUE 714 establishes a connection with a first eNB 704. In someembodiments, the first eNB 704 comprises a relay. The first eNB 704 maybe a UeNB that includes a UE and an eNB.

At step 1504, the TUE 714 determines a type of the first eNB 704. Forexample, the type of the first eNB 704 may be a relay eNB. As anotherexample, the type of the first eNB 704 may be either trusted oruntrusted. In such a case, trusted may indicate that a VPN connection isnot required and untrusted may indicate that a VPN connection isrequired. In an aspect, the type of the first eNB 704 may be advertisedby the first eNB 704 or may be based on an identifier, such as a publicland mobile network (PLMN) ID or a tracking area code (TAC).

At step 1506, the TUE 714 determines whether the type of the first eNB704 is a relay eNB (also referred to as a “UeNB”). If the first eNB 704is a UeNB (1506), then at step 1508, the TUE 714 establishes a VPNconnection with a gateway when the first eNB 704 relays data to a secondeNB 710. In an aspect, the gateway may be a Home agent and the VPNconnection may be a DSMIPv6 IPSec connection. In another aspect, thegateway may be an evolved packet data gateway (ePDG) and the VPN may bean IPSec tunnel. PDN data charges may be allocated based on datacommunicated over the VPN connection. A credit for PDN data may beprovided to the UeNB 704 based on the data communicated through the VPNconnection. If the first eNB 704 is not a UeNB (1506), the VPNconnection with the gateway is not established.

FIG. 16 is a conceptual data flow diagram 1600 illustrating the dataflow between different modules/means/components in an exemplaryapparatus 1602. The apparatus may be an eNB 710. The apparatus includesa module 1604 that receives requests from one or more of a TUE 712 or714. In one configuration, the request may be generated by the TUE 712or 714 and relayed to the eNB 710 by one of UeNB 702 or 704. Theapparatus 1602 further includes a module 1606 that processes therequests, a module 1608 that establishes connections with one or more ofa network entity, a UeNB 702 or 704 and a TUE 712 or 714, an accountingmodule 1610 that allocates charges for data and a transmission modulethat communicates with the with one or more of a network entity, a UeNB702 or 704 and a TUE 712 or 714.

The apparatus may include additional modules that perform each of thesteps of the algorithm in the aforementioned flow chart of FIG. 14. Assuch, each step in the aforementioned flow chart of FIG. 14 may beperformed by a module and the apparatus may include one or more of thosemodules. The modules may be one or more hardware components specificallyconfigured to carry out the stated processes/algorithm, implemented by aprocessor configured to perform the stated processes/algorithm, storedwithin a computer-readable medium for implementation by a processor, orsome combination thereof.

FIG. 17 is a diagram 1700 illustrating an example of a hardwareimplementation for an apparatus 1602′ employing a processing system1714. The processing system 1714 may be implemented with a busarchitecture, represented generally by the bus 1724. The bus 1724 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1714 and the overalldesign constraints. The bus 1724 links together various circuitsincluding one or more processors and/or hardware modules, represented bythe processor 1704, the modules 1604, 1606, 1608, 1610, 1612, and thecomputer-readable medium 1706. The bus 1724 may also link various othercircuits such as timing sources, peripherals, voltage regulators, andpower management circuits, which are well known in the art, andtherefore, will not be described any further.

The processing system 1714 may be coupled to a transceiver 1710. Thetransceiver 1710 is coupled to one or more antennas 1720. Thetransceiver 1710 provides a means for communicating with various otherapparatus over a transmission medium. The processing system 1714includes a processor 1704 coupled to a computer-readable medium 1706.The processor 1704 is responsible for general processing, including theexecution of software stored on the computer-readable medium 1706. Thesoftware, when executed by the processor 1704, causes the processingsystem 1714 to perform the various functions described supra for anyparticular apparatus. The computer-readable medium 1706 may also be usedfor storing data that is manipulated by the processor 1704 whenexecuting software. The processing system further includes at least oneof the modules 1604, 1606, 1608, 1610, and 1612. The modules may besoftware modules running in the processor 1704, resident/stored in thecomputer readable medium 1706, one or more hardware modules coupled tothe processor 1704, or some combination thereof. The processing system1714 may be a component of the eNB 610 and may include the memory 676and/or at least one of the TX processor 616, the RX processor 670, andthe controller/processor 675.

In one configuration, the apparatus 1602/1602′ for wirelesscommunication includes means 1604 for receiving a request related to aPDN connection from a first UE, means 1606 for processing the request,means 1608 for establishing or modifying a connection between a gatewayand the first UE in response to the request, means 1612 forcommunicating data between the first UE and the gateway on behalf of thesecond UE, and accounting means 1610 for allocating charges for datacommunicated between the first UE and the second UE.

The aforementioned means may be one or more of the aforementionedmodules of the apparatus 1602 and/or the processing system 1714 of theapparatus 1602′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1714 mayinclude the TX Processor 616, the RX Processor 670, and thecontroller/processor 675. As such, in one configuration, theaforementioned means may be the TX Processor 616, the RX Processor 670,and the controller/processor 675 configured to perform the functionsrecited by the aforementioned means.

FIG. 18 is a conceptual data flow diagram 1800 illustrating the dataflow between different modules/means/components in an exemplaryapparatus 1802. The apparatus may be UeNB 704. The apparatus includes amodule 1804 that receives information from a TUE 714 and a gateway viathe eNB 710, a module 1806 that relays data between the TUE 714 and thegateway, a module 1810 that determines and manages connections, a module1812 that establishes connections with the TUE 714, a module 1814 thatestablishes connections with the gateway, a module 1816 that transmitsdata to the TUE 714 and the gateway, and module 1808 that allocates datacharges based on data transmitted between the TUE 714 and the eNB 710.

The apparatus may include additional modules that perform each of thesteps of the algorithm in the aforementioned flow chart of FIG. 14. Assuch, each step in the aforementioned flow chart of FIG. 14 may beperformed by a module and the apparatus may include one or more of thosemodules. The modules may be one or more hardware components specificallyconfigured to carry out the stated processes/algorithm, implemented by aprocessor configured to perform the stated processes/algorithm, storedwithin a computer-readable medium for implementation by a processor, orsome combination thereof.

FIG. 19 is a diagram 1900 illustrating an example of a hardwareimplementation for an apparatus 1802′ employing a processing system1914. The processing system 1914 may be implemented with a busarchitecture, represented generally by the bus 1924. The bus 1924 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 1914 and the overalldesign constraints. The bus 1924 links together various circuitsincluding one or more processors and/or hardware modules, represented bythe processor 1904, the modules 1804, 1806, 1808, 1810, 1812, 1814,1816, and the computer-readable medium 1906. The bus 1924 may also linkvarious other circuits such as timing sources, peripherals, voltageregulators, and power management circuits, which are well known in theart, and therefore, will not be described any further.

The processing system 1914 may be coupled to a transceiver 1910. Thetransceiver 1910 is coupled to one or more antennas 1920. Thetransceiver 1910 provides a means for communicating with various otherapparatus over a transmission medium. The processing system 1914includes a processor 1904 coupled to a computer-readable medium 1906.The processor 1904 is responsible for general processing, including theexecution of software stored on the computer-readable medium 1906. Thesoftware, when executed by the processor 1904, causes the processingsystem 1914 to perform the various functions described supra for anyparticular apparatus. The computer-readable medium 1906 may also be usedfor storing data that is manipulated by the processor 1904 whenexecuting software. The processing system further includes at least oneof the modules 1804, 1806, 1808, 1810, 1812, 1814, and 1816. The modulesmay be software modules running in the processor 1904, resident/storedin the computer readable medium 1906, one or more hardware modulescoupled to the processor 1904, or some combination thereof. Theprocessing system 1914, or certain elements thereof, may be a componentof the eNB 610 and may include the memory 676 and/or at least one of theTX processor 616, the RX processor 670, and the controller/processor675. The processing system 1914, or certain elements thereof, may be acomponent of the UE 650 and may include the memory 660 and/or at leastone of the TX processor 668, the RX processor 656, and thecontroller/processor 659.

In one configuration, the apparatus 1802/1802′ for wirelesscommunication includes means 1812 for establishing a connection with aTUE while connected to a PDN through a collocated UE, means 1814 forestablishing or modifying a connection with a gateway, means 1806 forrelaying data between the TUE and the PDN using the established ormodified connection with the gateway, means 1808 for allocating chargesto the TUE based on the data relayed between the TUE and the PDN, means1804 for receiving data, means 1816 for transmitting data and means 1810for managing connection establishment means 1812 and 1814.

The aforementioned means may be one or more of the aforementionedmodules of the apparatus 1802 and/or the processing system 1914 of theapparatus 1802′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 1914 mayinclude the TX Processor 616, the RX Processor 670, and thecontroller/processor 675. As such, in one configuration, theaforementioned means may be the TX Processor 616, the RX Processor 670,and the controller/processor 675 configured to perform the functionsrecited by the aforementioned means.

In another configuration, the aforementioned means may be one or more ofthe aforementioned modules of the apparatus 1802 and/or the processingsystem 1914 of the apparatus 1802′ configured to perform the functionsrecited by the aforementioned means. As described supra, the processingsystem 1914 may include the TX Processor 668, the RX Processor 656, andthe controller/processor 659. As such, in one configuration, theaforementioned means may be the TX Processor 668, the RX Processor 656,and the controller/processor 659 configured to perform the functionsrecited by the aforementioned means.

FIG. 20 is a conceptual data flow diagram 2000 illustrating the dataflow between different modules/means/components in an exemplaryapparatus 2002. The apparatus may be a TUE 714. The apparatus includes amodule 2004 that receives data from a UeNB 704, a module 2012 thattransmits data to the UeNB 704, a module 2006 that provides informationused to allocate charges for received and transmitted data, a module2008 that establishes connections with one or more network entities, anda module 2010 that manages VPN connections.

The apparatus may include additional modules that perform each of thesteps of the algorithm in the aforementioned flow chart of FIG. 15. Assuch, each step in the aforementioned flow chart of FIG. 15 may beperformed by a module and the apparatus may include one or more of thosemodules. The modules may be one or more hardware components specificallyconfigured to carry out the stated processes/algorithm, implemented by aprocessor configured to perform the stated processes/algorithm, storedwithin a computer-readable medium for implementation by a processor, orsome combination thereof.

FIG. 21 is a diagram 2100 illustrating an example of a hardwareimplementation for an apparatus 2002′ employing a processing system2114. The processing system 2114 may be implemented with a busarchitecture, represented generally by the bus 2124. The bus 2124 mayinclude any number of interconnecting buses and bridges depending on thespecific application of the processing system 2114 and the overalldesign constraints. The bus 2124 links together various circuitsincluding one or more processors and/or hardware modules, represented bythe processor 2104, the modules 2004, 2006, 2008, 2010, 2012, and thecomputer-readable medium 2106. The bus 2124 may also link various othercircuits such as timing sources, peripherals, voltage regulators, andpower management circuits, which are well known in the art, andtherefore, will not be described any further.

The processing system 2114 may be coupled to a transceiver 2110. Thetransceiver 2110 is coupled to one or more antennas 2120. Thetransceiver 2110 provides a means for communicating with various otherapparatus over a transmission medium. The processing system 2114includes a processor 2104 coupled to a computer-readable medium 2106.The processor 2104 is responsible for general processing, including theexecution of software stored on the computer-readable medium 2106. Thesoftware, when executed by the processor 2104, causes the processingsystem 2114 to perform the various functions described supra for anyparticular apparatus. The computer-readable medium 2106 may also be usedfor storing data that is manipulated by the processor 2104 whenexecuting software. The processing system further includes at least oneof the modules 2004, 2006, 2008, 2010, and 2012. The modules may besoftware modules running in the processor 2104, resident/stored in thecomputer readable medium 2106, one or more hardware modules coupled tothe processor 2104, or some combination thereof. The processing system2114 may be a component of the UE 650 and may include the memory 660and/or at least one of the TX processor 668, the RX processor 656, andthe controller/processor 659.

In one configuration, the apparatus 2002/2002′ for wirelesscommunication includes means 2008 for establishing a connection with afirst eNB, means 2010 for establishing a virtual private network (VPN)connection with a gateway when the first eNB relays data to a secondeNB, means 2006 for optionally identifying data transfers subject to PDNdata charges, means 2012 for transmitting data, and means 2004 forreceiving data.

The aforementioned means may be one or more of the aforementionedmodules of the apparatus 2002 and/or the processing system 2114 of theapparatus 2002′ configured to perform the functions recited by theaforementioned means. As described supra, the processing system 2114 mayinclude the TX Processor 668, the RX Processor 656, and thecontroller/processor 659. As such, in one configuration, theaforementioned means may be the TX Processor 668, the RX Processor 656,and the controller/processor 659 configured to perform the functionsrecited by the aforementioned means.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed is an illustration of exemplary approaches. Basedupon design preferences, it is understood that the specific order orhierarchy of steps in the processes may be rearranged. Further, somesteps may be combined or omitted. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed as a means plus functionunless the element is expressly recited using the phrase “means for.”

What is claimed is:
 1. A method of wireless communication, comprising:receiving a request related to a packet data network (PDN) connectionfrom a first user equipment (UE), wherein the request relates to asecond UE; and establishing or modifying a connection between a gatewayand the first UE in response to the request, wherein establishing ormodifying the connection includes sending an identifier of the second UEto the gateway.
 2. The method of claim 1, further comprising allocatingcharges to the second UE for data communicated between the first UE andthe gateway on behalf of the second UE.
 3. The method of claim 2,wherein the charges are allocated to the second UE based on theidentifier of the second UE.
 4. The method of claim 2, whereinallocating charges for data includes providing a credit to the first UEfor data communicated on behalf of the second UE.
 5. The method of claim1, wherein establishing a connection between the gateway and the firstUE includes: receiving a request for a PDN connection, the requestincluding an identifier of the first UE; and creating a radio bearer forthe requested PDN connection.
 6. The method of claim 5, wherein therequest related to the PDN connection includes the identifier of thesecond UE.
 7. The method of claim 1, wherein modifying a connectionbetween the gateway and the first UE includes sending a traffic flowtemplate (TFT) to discriminate between data corresponding to the secondUE and data corresponding to another UE.
 8. The method of claim 1,wherein modifying a connection between the gateway and the first UEincludes creating a radio bearer associated with the second UE.
 9. Anapparatus for wireless communication, comprising: means for receiving arequest related to a packet data network (PDN) connection from a firstuser equipment (UE), wherein the request relates to a second UE; andmeans for establishing or modifying a connection between a gateway andthe first UE in response to the request, wherein establishing ormodifying the connection includes sending an identifier of the second UEto the gateway.
 10. The apparatus of claim 9, further comprising meansfor allocating charges to the second UE for data communicated betweenthe first UE and the gateway on behalf of the second UE.
 11. Theapparatus of claim 10, wherein the charges are allocated to the secondUE based on the identifier of the second UE.
 12. The apparatus of claim10, wherein the means for allocating charges for data provides a creditto the first UE for data communicated on behalf of the second UE. 13.The apparatus of claim 9, wherein the means for establishing aconnection between the gateway and the first UE is configured to receivea request for a PDN connection, the request including an identifier ofthe first UE, and is further configured to create a radio bearer for thePDN connection.
 14. The apparatus of claim 13, wherein the requestrelated to the PDN connection includes the identifier of the second UE.15. The apparatus of claim 9, wherein the means for modifying aconnection sends a traffic flow template (TFT) to discriminate betweendata corresponding to the second UE and data corresponding to anotherUE.
 16. The apparatus of claim 9, wherein the means for modifying aconnection between the gateway and the first UE creates a radio bearerassociated with the second UE.
 17. An apparatus for wirelesscommunication, comprising: a processing system configured to: receive arequest related to a packet data network (PDN) connection from a firstuser equipment (UE), wherein the request relates to a second UE; andestablish or modify a connection between a gateway and the first UE inresponse to the request, wherein the processing system sends anidentifier of the second UE to the gateway when establishing ormodifying the connection.
 18. A computer program product, comprising: acomputer-readable non-transitory medium comprising code for: receiving arequest related to a packet data network (PDN) connection from a firstuser equipment (UE), wherein the request relates to a second UE; andestablishing or modifying a connection between a gateway and the firstUE in response to the request, wherein establishing or modifying theconnection includes sending an identifier of the second UE to thegateway.
 19. A method of wireless communication, comprising:establishing a connection with a terminal user equipment (TUE) whileconnected to a packet data network (PDN) through a collocated userequipment; establishing or modifying a connection with a gateway,wherein establishing or modifying the connection includes sending anidentifier of the TUE to the gateway; and relaying data between the TUEand the PDN using the established or modified connection with thegateway.
 20. The method of claim 19, wherein PDN charges are allocatedto the TUE based on the data relayed between the TUE and the PDN. 21.The method of claim 19, further comprising receiving a credit based onthe data relayed between the TUE and the PDN.
 22. The method of claim19, wherein establishing or modifying a connection with the gatewayincludes requesting a radio bearer associated with the TUE.
 23. Themethod of claim 19, wherein modifying a connection with the gatewayincludes sending a traffic flow template (TFT) to discriminate betweendata corresponding to the TUE and data corresponding to another UE. 24.An apparatus for wireless communication, comprising: means forestablishing a connection with a terminal user equipment (TUE) whileconnected to a packet data network (PDN) through a collocated userequipment; means for establishing or modifying a connection with agateway, wherein the means for establishing or modifying the connectionsends an identifier of the TUE to the gateway; and means for relayingdata between the TUE and the PDN using the established or modifiedconnection with the gateway.
 25. The apparatus of claim 24, wherein PDNcharges are allocated to the TUE based on the data relayed between theTUE and the PDN.
 26. The apparatus of claim 24, wherein a credit isreceived for the data relayed between the TUE and the PDN.
 27. Theapparatus of claim 24, wherein the means for establishing or modifying aconnection with the gateway requests a radio bearer associated with theTUE.
 28. The apparatus of claim 24, wherein the means for modifying aconnection with the gateway sends a traffic flow template (TFT) todiscriminate between data corresponding to the TUE and datacorresponding to another UE.
 29. An apparatus for wirelesscommunication, comprising: a processing system configured to: establisha connection with a terminal user equipment (TUE) while connected to apacket data network (PDN) through a collocated user equipment; establishor modify a connection with a gateway wherein the processing system isconfigured to send an identifier of the TUE to the gateway whenestablishing or modifying the connection; and relay data between the TUEand the PDN using the established or modified connection with thegateway.
 30. A computer program product, comprising: a computer-readablenon-transitory medium comprising code for: establishing a connectionwith a terminal user equipment (TUE) while connected to a packet datanetwork (PDN) through a collocated user equipment; establishing ormodifying a connection with a gateway, wherein establishing or modifyingthe connection includes sending an identifier of the TUE to the gateway;and relaying data between the TUE and the PDN using the established ormodified connection with the gateway.
 31. A method of wirelesscommunication, comprising: establishing a connection with a firsteNodeB; determining a type of the first eNodeB; and establishing avirtual private network (VPN) connection with a gateway when the firsteNodeB relays data to a second eNodeB.
 32. The method of claim 31,wherein PDN data charges are allocated based on data communicated overthe VPN connection.
 33. The method of claim 32, wherein the type of thefirst eNodeB is determined to be a relay.
 34. The method of claim 32,wherein the type of the first eNodeB is determined to be one of trustedor untrusted.
 35. An apparatus for wireless communication, comprising:means for establishing a connection with a first eNodeB; means fordetermining a type of the first eNodeB; and means for establishing avirtual private network (VPN) connection with a gateway when the firsteNodeB relays data to a second eNodeB.
 36. The apparatus of claim 35,wherein PDN data charges are allocated based on data communicated overthe VPN connection.
 37. The apparatus of claim 36, wherein the type ofthe first eNodeB is determined to be a relay.
 38. The apparatus of claim36, wherein the type of the first eNodeB is determined to be one oftrusted or untrusted.
 39. An apparatus for wireless communication,comprising: a processing system configured to: establish a connectionwith a first eNodeB; determine a type of the first eNodeB; and establisha virtual private network (VPN) connection with a gateway when the firsteNodeB relays data to a second eNodeB.
 40. The apparatus of claim 39,wherein PDN data charges are allocated based on data communicated overthe VPN connection.
 41. A computer program product, comprising: acomputer-readable non-transitory medium comprising code for:establishing a connection with a first eNodeB; determining a type of thefirst eNodeB; and establishing a virtual private network (VPN)connection with a gateway when the first eNodeB relays data to a secondeNodeB.
 42. The computer program product of claim 41, wherein PDN datacharges are allocated based on data communicated over the VPNconnection.